Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

SkyEcho 2 with Skydemon - ghost plane


Author
Message
chris-bayern
c
Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)
Group: Forum Members
Posts: 6, Visits: 53
Some weeks ago I switched from Stratux to the SkyEcho 2. So far it works very well in combination with SkyDemon. I use the SkyEcho 2 only as receiver for ADS-B and FLARM. And I am not always flying the same aircraft and so I can't store the FLARM and ADS-B hex code in the SkyEcho 2 or I would have to adjust both frequently (see post "SkyEcho Set Aircraft Reg and Hex Code from Skydemon"). So it happens that at the beginning of a flight I hear permanent traffic warnings (ghost plane) - which can be very "stressful" (see post "Suppress traffic warnings below a certain height"). I know that I can ignore a aircraft (with one touch on the Traffic Radar). But on ground I often can't decide which aircraft should be ignored.

Before the SkyEcho 2 I had a Stratux in use. And back then I had no problems with a "ghost plane" (not even when changing the aircraft). In the SkyDemon "Aircraft Profile" I had always stored the FLARM HEX ID. But the SkyEcho 2 doesn't seem to transmit a FLARM HEX ID to SkyDemon when Flarm is used (received). You see only the text "FLARM" in the Traffic Radar. This seems to be the difference between Stratux and SkyEcho 2.

Can this be fixed?

Replies
Tim Dawson
Tim Dawson
SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)SkyDemon Team (690K reputation)
Group: Forum Members
Posts: 8.2K, Visits: 9.7K
With SkyEcho 2 we decode the FLARM data ourselves, and we do not currently offer a facility to ignore an aircraft identifier that is a pure FLARM id. Perhaps the device you were using previously, which I gather decodes FLARM itself without a license, offered that functionality as part of its features.
chris-bayern
c
Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)Too Much Forum (131 reputation)
Group: Forum Members
Posts: 6, Visits: 53
Tim Dawson - 11/4/2020 9:16:22 AM
With SkyEcho 2 we decode the FLARM data ourselves, and we do not currently offer a facility to ignore an aircraft identifier that is a pure FLARM id. Perhaps the device you were using previously, which I gather decodes FLARM itself without a license, offered that functionality as part of its features.


I think this is the cause. I am pretty sure that STRATUX sent the FLARM ID with the GDL90. So the filter in the SkyDemon aircraft profile could hide it. But I read (different thread) that an update is planned in connection with the SkyEcho 2. SkyEcho 2 itself has the ability to store a FLARM and an ADS-B ID (to hide them). Maybe it is then possible to fill in both fields in SkyEcho 2 (at connection start-up) with the data stored in the SkyDemon aircraft profile.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Reading This Topic

Login

Explore
Messages
Mentions
Search